Test mode operations

You can perform various operations in test mode like running a process, retrying a previous test and others.

Running a process in test mode

When you test a process, you can see the progress and the results as each step is tested.

1. Open a process.

2. Click Test above the upper right corner of the canvas.

3. If you enter test mode and have made a change to the process without saving it, you receive a message. Select one of the following:

   • Click Revert and Reload.

   • Click Save.

   • Click Cancel.

4. In the Test window, select the Runtime on which the process should execute.

   note

   If you do not have a Runtime installed, you are prompted to install one before continuing.

5. If extensions are enabled for your account, click the Test Extensions arrow to configure extension values.

6. Click Run Test.

   The process canvas background turns gray, indicating that you are in test mode. You cannot edit the process.

   note

   If the process (and any subprocesses within the process) contain a large number of components, a message warning that the test run might take a long time to complete is displayed.

   While a step is being tested, it is highlighted in yellow. If an error occurs, an error message dialog opens, and the step is highlighted in red. If the step passes the test, it is highlighted in green, and the test continues to the next step in the process.

   If the process exceeds the maximum number of messages that a test execution can generate, warning messages inform you that logging was truncated and/or step execution tracking was truncated. You also receive a message telling you whether the execution completed successfully or failed. The first untested step is highlighted in dark gray. The steps that follow have no highlighting. The status of each document is reported in the Documents pane.

   note

   For processes (or subprocesses within a process) that include a Process Route component, test mode runs without explicitly deploying the process route or any of its referenced processes.

   Retrying a previous test is a faster alternative than rerunning a test from scratch.

Retrying a previous test in test mode

When developing new processes, Test mode is an important debugging tool. If you are continually making updates to a process, you can choose to retry previous tests. This prevents you from having to rerun the test from scratch and continually access the source system to bring documents into the process flow. This is helpful, for example, when your connector operation is set to get and delete inbound documents so you do not need to continually reset the data in your source system.

Procedure

1. Assuming that you have run a previous test and the process is still open in test mode, click the drop-down arrow next to the process name and select Retry Previous Test.

2. Select the desired test execution from the first list box.

3. Click the arrow next to Documents to display the documents available to be retried.

4. Turn on the check boxes next to the documents to be retried.

5. Click the arrow next to Test Extensions and update the test extension values as needed.

6. Click Run Test.

   note

   Previous test documents are accessible only when the process is open. Closing the process erases the queue of test executions and you need to rerun and get documents from your source connector.

   After testing, return to Edit mode.

Exiting test mode

1. After testing, return to Edit mode.

2. Click the back button next to the process name to return to Edit mode.

   The process canvas background turns white, indicating that you are in Edit mode.

caution

The log and data files produced during a Test mode execution are temporary. After you exit Test mode, this information is lost.